Network adapted for mobile devices

ABSTRACT

A network mobility server, which includes a target device inventory module, a data collection module, a data management module and a distribution module. The data management module, includes at least one data storage module, in which at least a portion of the data stored therein are identical data items stored in different selected formats suitable for use on mobile computing and telecommunication devices. The network also includes network agents, resident on numbers of the network members.

RELATED APPLICATION

This is a continuation application of U.S. application Ser. No.11/238,839 filed 29 Sep. 2005, which claims the benefit of U.S.Provisional Patent Application No. 60/715,415 filed 9 Sep. 2005. Theseapplications are incorporated herein by reference for all purposes.

BACKGROUND

This application relates to the field of networks of computers andallied devices, and more specifically to networks that specificallyinclude mobile devices.

A number of trends are converging to impact computer networks and theways in which their users interact. Perhaps most important is theincreasing capability of mobile devices, such as cellular telephones,mobile email devices (most notably those sold under the BlackBerrytrademark), and personal data assistants (PDA's). Devices actuallylabeled “computers” are shrinking rapidly in size, having alreadyevolved from “portable” to “laptop” to “notebook” in size.Multi-function devices are now common—BlackBerry brand devices nowinclude cellular telephones, and both they and most cellular telephonedevices now include internet browsers as integral standard equipment.

This technical evolution has been accompanied by increasing use of, andreliance upon, such devices by business persons. The general expectationhas arisen that a businessperson should be connected by telephone, emailand internet at all times and all places.

Rising equipment capabilities have not been accompanied by an equivalentincrease in operational capabilities, however. One may be able to use acellular telephone handset to connect with her business LAN, forexample, but the network will persist in treating her as a “computer”user, sending data in a format aimed at a “computer” display. Evenemail-capable mobile devices, such as those sold by Nokia, which canaccept and handle plain text, cannot handle many common document types,such as Microsoft Excel spreadsheets, in a usable manner.

Another aspect of that problem is seen in the fact that many businessesand individuals are amassing data by the terabyte, yet that data islargely inaccessible by mobile users. Even if a person can gain accessto a conventional network using his BlackBerry device, for example, thefact that the network is designed for “computer” users limits hisability, working over a mobile telephone signal, to take advantage ofnetwork features. Today mobile users are typically supposed to copy theinformation they will need onto their mobile devices before they leavethe office or home environment, subject to the storage limitations onthe mobile devices, which leaves no room to handle unforeseen needs forother information while being mobile.

Frustration is compounded by the fact that his data is most probablybacked up on a central server. Backup systems, however, are generallydesigned for the sole purpose of storing data, and their functionalityis limited to restoring that data, most often only on the equipment fromwhich it was originally stored, or a substitute.

The shortcomings of conventional networks not only impact usersthemselves, but also users' interactions with those around them. Acommon scenario when a business person is away from her home base is aneed to share data with a business partner or associate from a differentorganization. Often, both persons are operating mobile, and what isneeded is a capability to use on-hand devices, from the group notedabove, to search for, located, transmit and receive data. The problem isoften compounded by the fact that mobile device software is generallyprovided by the network provider, so that even if a user could manage toreceive data formatted for her device, she would have problems sharingthat data with someone operating on a different network. Withconventional networks, all one can do is wait until a network-capableservice is available.

At bottom, conventional networks are designed to accommodate mobiledevices only to the extent that those devices emulate desktop computers.What is needed is a network specifically designed to service bothdesktop and mobile equipment, one that allows a mobile user to take fulladvantage of network functionality from a mobile device. One aspect ofsuch a network should be the seamless provision of data in a manner thatfully accommodates a device's memory and screen capabilities. Anotheraspect of such a network would be the continuous access to user data,with complete search, download and forwarding capabilities.

SUMMARY OF THE INVENTION

One aspect of the invention is a network mobility server, which includesa target device inventory module, a data collection module, a datamanagement module and a distribution module. The data management module,includes at least one data storage module, in which at least a portionof the data stored therein are identical data items stored in differentselected formats suitable for use on mobile computing andtelecommunication devices. In a further aspect of the invention, thenetwork also includes network agents, resident on numbers of the networkmembers.

Another aspect of the invention is a network adapted for mobile devices.The network includes a number of fixed component network members, havinggenerally fixed locations, each having sufficient computing power torender data files into multiple formats. It also includes a number ofmobile component network members, each having a size suitable formovement with a user and having insufficient computing power to renderdata files into multiple formats. A network mobility server is adaptedfor communicating with the fixed and mobile component members, andadapted for receiving and storing data in formats suitable fortransmission to the mobile component members.

Other features and aspects of the invention are described in the claimsappended hereto, which solely define the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic representation of a mobile service network inaccordance with the present invention.

FIG. 2 is a functional block diagram of the mobility server component ofa network in accordance with the present invention.

FIG. 3 is a functional block diagram of a network agent component of anetwork in accordance with the present invention.

FIG. 4 a is a flowchart depicting the network agent portion of anautomatic backup process in accordance with the present invention.

FIG. 4 b is a flowchart depicting the mobility server portion of anautomatic backup process in accordance with the present invention.

FIG. 5 is a flowchart depicting a data distribution process inaccordance with the present invention.

DETAILED DESCRIPTION

The following detailed description refers to the figures. Thedescription addresses a number of embodiments, which are presented toillustrate, not to limit, the scope of the claim, which alone define theinvention. Many aspects of the implementation of the invention will beclear to those of ordinary skill in the art, and such persons willrecognize and understand such details, as well as how to implementequivalent solutions known in the art.

A private mobile network (“PMN”) 10 in accordance with the presentinvention is shown in FIG. 1. The network is heterogeneous, including anumber of member types. Generally, the PMN can be divided into threebroad portions. Fixed components 12 are generally those network memberswhose locations do not change, such as desktop PC's 15. Desktop PC's canaccess the PMN through the communication channels of a local areanetwork (“LAN”) 18, or independent desktop PC's 20 can employ directcommunication channels. Alternatively, members of a LAN may access thatnetwork, and thence the PMN, via a remote virtual private network(“VPN”) 17. The various communication modes shown here form no part ofthe invention and are well known to those in the art.

Mobile components 16 consist of devices that are likely to travel withtheir users, such as cellular telephones 24, email-enabled integrateddevices 26 such as that sold under the BlackBerry trademark, or PersonalDigital Assistant devices 28. It should be noted that the foregoing listof mobile devices addresses devices in wide use at the time the presentapplication is written; undoubtedly the future will bring changes tothat list, without affecting the invention claimed herein. laptop

It should be noted that the division of PMN members into categories of“fixed” and “mobile” is not susceptible to hard and fast divisions. Forexample, laptop or notebook PC's may be employed as fixed devices 22,which may include docking stations or external devices, such as storagedevices, to enhance capabilities, or as true mobile devices 30, movingwith a user as desired. To some extent the division is based uponcapabilities, as will be further seen below. For example, fixedcomponents will often be able to perform data rendering locally, freeingmobile or server assets from that task. Also, to some extent thedivision is based more on the role being played by a given device at agiven time. Most PMN users are expected to utilize both fixed and mobilenetwork components, and a primary expected utility of the presentinvention will be to facilitate data access and transfer between auser's fixed and mobile devices, as discussed below.

Mobility Server

The central node of the PMN is the mobility server 14, shown infunctional block form in FIG. 2. The primary components of the mobilityserver are communication module 110, security module 120, target deviceinventory module 130, data collection module 140, distribution module150, data management module 160 and change management module 170. Thefollowing discussion sketches out the general functions of the mobilityserver components, and a more detailed discussion accompanies thedescription of specific processes, below.

Communication module 110 manages the communication between the mobilityserver and both fixed and mobile components of the PMN. This moduleprovides communication services for the remainder of the serverfunctionality, utilizing various communication channel adapters, such asadapters for HTML 111, XHTML 112, WAP 113, RSS 114, Email 115, IM 116,and SMS 117. Those in the art will understand that the foregoing list isillustrative only, in that communications channels will change overtime, and adapters will be provided in the art to accommodate the same.The functional requirement and operation of a communications modulewill, however, remain.

It is important to emphasize that although it is convenient andconventional to depict functional blocks as independent entities, theseelements continually interact during operation of the mobility server.For example, the communications tasks performed communication module 110require cooperative action with a number of other components, as willbecome clear as the discussion progresses below. To note a singleexample, communication often requires that data be reformatted for theparticular needs of mobile devices such as memory and screen-size, sothat the assembling and transmission of an HTML document may requirerendering of embedded graphics to accommodate the needs of a givenmobile device. Other examples will be clear to those in the art.

Security module 120 provides security services, generally in keepingwith the requirements of the art. Necessary subunits provided here wouldinclude encryption/decryption module 122, firewall 124, andanti-virus/anti-span module 126. To a large extent the details of thesecurity module, as well and implementation details, are dictated by thestate of the art of network security systems. Although many networksystems do not perform anti-virus and anti-spam screening as informationtravels through the network, those steps would be standard here. It isexpected that the state of that art will change over time, and suchchanges will be implemented without affecting the scope of the presentinvention. It can be noted that a range of options is available in thefield of encryption/decryption systems and devices. It is preferred toemploy 128-bit encryption in this application.

Two other modules provide particular to the invention. Permissionsmodule 121 maintains a register of permission linkages that enablewidespread and flexible sharing of data across the system. Having suchdata readily available facilitates sharing information between networkmembers, while maintaining a secure environment. New member module 123is designed to allow the rapid and simple addition of new members, someon a provisional basis, to enable the rapid sharing of information. Forexample, this facility permits a member who desires to transferinformation to a business acquaintance while at a remote location tobring the acquaintance quickly into the network and initiate the desiredfile transfer or sharing.

Target device inventory 130 tracks network member devices regarding eachdevice's ability to accept data in various formats, as well as thatdevice's capability to render data in various forms. Such information isgenerally gathered during a network member's initial configuration or aschange information by a member. This module interacts with profile store166 to store device-related data.

Within the target device inventory, a format criteria register 132maintains information about the format in which various data types mustbe presented to each device or specific users device, together withbasic device information such as the amount of memory available, thescreen type and size. For example, mobile devices may not be able todisplay formatted text from word processing programs such as MicrosoftWord, or spreadsheets from programs such as Microsoft Excel. Sendingdata in such native formats does a user no good, as at best theyregister is having been received but cannot be displayed. Similarly,rendering capability register 134 tracks the rendering capabilities ofeach network member. Taking the previous example one step further, ifone wishes to transmit a spreadsheet to a mobile phone, the spreadsheetmust be rendered in a format that the handset can receive and display.Converting the spreadsheet to that format at the point of origin maywell be the fastest and most efficient way to accomplish that goal, andthus knowing whether that capability exists at the originating member isa key data item.

Data collection module 140 oversees the collection of data from networkmembers into the storage system. As discussed in more detail inconnection with FIG. 4 below, incoming data is not simply dumped intothe data storage system. Rather, the data collection module, operatingthrough the Format Manager 142, determines where data is to be stored,what formats it will be stored in, and other operations set out below.

Distribution module 160 handles the distribution of data from themobility server to network members, as discussed more fully inconnection with FIG. 5 below. Two subunits assist in this function: arendering module 152 performs the rendering function, translating datafrom one format to another, as required. A separate functionality isprovided by streaming module 154, which provides the capability tostream data directly from the mobility server to the user. This lattercapability is particularly useful for media such as video or soundfiles, as it allows a member direct access to such media, rather thanhaving to download and later find a suitable device on which to run thefile.

Data management module 160 occupies a key position in the system, as itmanages the actual storage process. Many of the operations of thismodule are set out in connection with detailed discussion of processes,below. Five data storage units perform the actual storagefunctions—primary data store 162, with the central index 164; memberprofile store 166; metadata store 167; and version manager 168. Thecentral data store and its associated index comprise a large-scaledatabase system, capable of storing data in any format, withstate-of-the-art indexing, search and retrieval capabilities. Suchdatabase systems are well-known in the art, supplied by vendors such asOracle, Microsoft, MySQL and the like. Such systems can be adapted tothe ends described herein, and as technology develops, more capabledatabase systems may be implemented in their place, all within the scopeof the present invention. It should be noted that data management module160 handles the most critical data tasks for the system, but many othersubsystems perform their own data management activities. Security module120, for example, maintains data concerning permissions, new memberactivities, etc.

Member profile store 166 is a separate data store devoted to the task ofhandling member-related information. A separate system is devoted tothis task because dealing with member information rapidly andefficiently is a mission-critical task in this system, made morecomplicated by the mix of mobile and fixed devices. This database storesall member-specific data items, including fixed personal data (name,address, etc.), device information associated with a member (equipmentID, memory capacity, screen capacity, rendering capacity, etc.) andactivity information (alert triggers and history, tracking history).

Metadata store 167 is likewise an important aspect of the system.Metadata includes a variety of information about the data itself, suchas permissions, sharing information, monitoring or alert information, orchange information, to list a few possible types. In the present system,metadata becomes more important than in other types of systems, as thesystem is designed to promote data sharing and data accessibility. Also,the emphasis on mobile users places a premium on network speed andflexibility.

Version manager 168 oversees the storage and tracking of documentversions, as discussed more fully below. A number of technologies areavailable to those in the art, who will understand how best to implementa suitable system.

Change management module 170 monitors documents and data across thenetwork, to provide two key functions. First, tracking module 172monitors all actions taken regarding a document by a member. Forexample, if a document is delivered to a user, who then opens thedocument, makes changes to the document and then forwards the documentto a third party, all of those actions are recorded by the trackingmodule. Tracking results are stored in the profile store 166. Alertingmodule 174 calls users' attention to the occurrence of specified events,such as document actions noted above or actions in the environment. Bothprocesses are described more fully below, in connection with FIG. 5.

The mobility server is installed and operated in a large-scale datacenter, based on well-known design and operating standards. Oneembodiment of the mobility server, for example, would employ anarchitecture that groups physical servers into server cells for optimumstorage and administration. Such a system would preferably utilizeservers with dual processors operating at state-of-the-art clock rates,such as 3 Ghz; dual gigabit network cards; and mass storage capabilitysuch as 12 250 GB disks in Raid5 configuration, providing a total of 2.5TB storage capability. Those in the art understand that such equipmentcan be obtained from vendors such as 3Ware and the like. It is preferredto employ a Linux operating system and MySQL as a database server, withAFS (Andrew File System), a Unix/Linux based file system allowingmapping of all drives available in a Server Cell into a single logicalfile system. Other details of the preferred system are well-known in theart. Another embodiment of the present invention could employ aconsiderably less sophisticated or elaborate hardware landscape, as willbe understood by those in the art.

Network Agent

The mobility server is assisted by network agent 16, resident on eachnetwork component (or “host” component) capable of mounting suchsoftware. The agent acts as a network client on all fixed networkcomponents and those mobile components, such as laptops and PDA's thatwill accept client software.

The agent interfaces to the mobility server through SecurityInfrastructure 240. This element includes a firewall 244 as well asencryption service 242 and anti-spam/anti-virus subsystems 242 and 246.These services can be configured as supplemental to, or in lieu of,similar systems on the host system.

Desktop API 220 integrates agent functionality to the operations of thehost computer, and such API's are furnished as required to providecompatibility with various PC architectures and desktop applicationsbeing offered. One API, for example, would allow the agent to operatewithin a Microsoft Windows environment, while others would provide foroperation in Apple Macintosh and Linux environments. The API mustprovide clear and accessible interface points to allow the creation ofadditional desktop adapters to integrate with emerging desktopfunctions.

The desktop adapters 210 provide the working interfaces between theagent and applications running on the local host, such as wordprocessing, office support and other applications. These modules arewritten under the API to allow tight integration to key desktopfunctionality, such as the file system adapter 211, Microsoft Outlookadapter 212, search engine adapter 213, CRM (Customer RelationshipManagement) system adapter 214, document management system adapter 215,and other adapters 216. The system is designed for easy development ofnew or improved adapters as required by technology developments. Itshould be noted that desktop adapters not only integrate withapplications running on the local hardware (such as Microsoft Outlook,for example), but also with applications such as CRM, which may beoperating in a client-server or pure web-based configuration butaccessible from the desktop.

Client services module 230 performs both operational and administrativeservices for the system. Operationally, this module oversees the localportion of the automatic backup process, described below in connectionwith FIG. 4 a. Administratively, this module provides a number ofservices that ensure efficient operation of the system. For example,balancing workload is an important task, so that this module operates inconjunction with similar modules at the mobility server level toschedule and allocate tasks to optimize both functionality andefficiency. Timing of data communication activities, such as uploadingand downloading, which typically require high bandwidth, can be spreadto off-peak times to smooth the load on scarce resources. The agent andsimilar control systems on the server would cooperate to balanceworkload at both the local host and the server, allocating tasks tolocations that can best handle them under the existing conditions ofworkload and traffic. Such activities are within the knowledge of thosein the art. The preferred form of the agent further ensures tightintegration between the agent and the host system by providing robustmultithreaded monitoring in the client services module.

Rendering is such a key aspect of the present invention that a renderingmodule 232 is devoted to managing that activity at the local level. Aswill be seen in connection with both the automatic backup anddistribution processes, described in detail below, data is provided tothe network in a variety of formats. Generally it will be preferable toperform rendering operations at the local level to conserve serverresources and to minimize costs to the individual user.

Agents will be installed on all network members capable of receivingthem. It is generally expected that all fixed component members willhave a resident agent. Clearly, all laptop devices will likewise haveagents installed, as will those PDA's that can usefully accept suchsoftware. At the far end of the spectrum, cellular telephone handsetswill interact with the network on whatever communication channels areprovided, primarily via SMS, as well as taking advantage of the browsercapability provided integral with such devices. Over time it is expectedthat such devices will become more capable, and agents will be providedfor such devices as they evolve.

While the description above sets out aspects of an embodiment of theinvention, it should be clear that the invention can be implemented in awide variety of specific forms. For example, the mobility serverfunctionality could be implemented as a conventional server/data centeras described above, or it could be structured in a more distributedfashion. The server itself could be structured conventionally, or itcould be fashioned under any of the emerging architectures, such as webservices, enterprise service architecture, or others. A software-basedsystem is described here, but those in the art understand that the sameresults could be achieved with a hardware implementation or hybrid(firmware) structure. The network agent, in particular, is apt toundergo considerable alteration from the details described above, giventhat technology will likely evolve to allow ever greater functionalityin ever smaller packages, increasing the ability to incorporate networkagent functionality in more and more mobile network members.

In general, the network includes fixed component members, broadlydefined as those able to render data in multiple formats; mobilemembers, which travel with their users; and a central hub that storesinformation in multiple formats and provides it to users in formatsspecifically tailored to the needs of their system.

Automatic Backup/Virtual Publication

The process of automatically backing up data from a network member isdepicted in FIGS. 4 a and 4 b. This process serves a number of separateobjectives. The task of backing up work from a user, immediately andautomatically, is the most straightforward, but unlike prior artsystems, the present backup method not only backs up data, but also itvirtually publishes data in a manner suitable for use on a variety ofmobile formats. It should be understood that the term “publish” as usedhere does not denote actual publication to mobile users, but rather thisaspect of the invention makes such publication possible. There being noexact term in the art that exactly fits the present invention, the term“virtual publication” is adopted to describe this process of makingformatted data available for later use.

It is also important to distinguish between virtual publication, asshown here, and data backup. The former term implies the provision ofdata formatted for mobile users, formats generally different from thenative data format. This term also implies accessibility by other users.Backup, on the other hand, implies the full storage of all data selectedfor backup. Moreover, to the extent that backup occurs in some formatother than the native data format (a compressed format, for example),that format change generally is hidden from the user, as the data isbacked up from the native format and is restored to the same.

As will be seen below, users can engage in both data backup and virtualpublication, in any combination of those activities. A user with accessto existing backup storage, for example, could elect to virtuallypublish data without backup. Conversely, a user with no need tocommunicate to mobile users could elect only to engage in backupactivities. Full use of the aspects of the invention presented here,however, entail both backup and virtual publication.

According to an aspect of the present invention, backup activities occurat both the agent (local) and mobility server (network) levels. Stepsshown in FIG. 4 a take place at the agent, while FIG. 4 b depictsactions at the network. This process is executed by data client servicesmodule 230 of the agent (FIG. 3).

The network agent continuously performs step 302, monitoring the hostsystem for data changes. This step is accomplished as a result ofintegration with the host, and those in the art will understand thevarious methods for implementing such functionality. When a change isdetected, at step 304, the system then determines whether the change inquestion should trigger a backup action, at decision step 306. Thatdecision can be performed in a number of conventional methods, usingtables, options and similar known functionalities. Alternatively, theuser might expressly desire to virtually publish a document or file, inwhich case a virtual publication request would likewise occur at step304.

Step 306 determines whether the data that has been changed by the usershould be backed up. Of course, an express virtual publication requestwould return a “yes” at this point with no further analysis. In oneembodiment of the invention, decision steps such as step 306 aregoverned by backup parameters, predefined by the user. The key variablesaddress questions of what documents to back up and when to do so. Thevirtual publishing aspect of this process also calls for the user tospecify (either in connection with backup parameters or more generaluser preferences) the likely recipients of data, as well as any specialhandling or security concerns. Thus, in one aspect of the invention, auser may specify that photographs and videos (which could be identifiedby file types JPG and AVI, for example) may be accessed by a wide groupof users, while word processing documents and spreadsheets are availableonly to a select group.

Once it is determined that the data file, or document, in question is tobe backed up, the agent determines transmission parameters at step 308.These parameters primarily concern whether the data file will betransmitted in its entirety, or only changes will be sent. Also, thesystem determines what format to employ, and whether multiple copies ofthe data should be forwarded. The latter factor allows the system toprepare to serve multiple users, on equipment of varying power. Forexample, a graphics file could be backed up in three formats—a nativeformat file (for example, JPEG, PSD, etc.) at the image size andresolution originally employed; a thumbnail file suitable forpreviewing; and a low-resolution, small image file suitable for devicessuch as cellular telephone handsets. Or, formats such as MicrosoftExcel, which are difficult for many mobile devices to display, can alsobe stored as plain text files or pdf documents. The agent makes suchdeterminations by interacting with profile data store 310, whichcontains user preferences as well as system rules and guidelines.

The determinations of step 308 result in a set of formats in which thedata will be stored, which in turn drives the format loop of decisionstep 312 and reformatting step 314. Several reformatting iterations maybe required, as in the graphics example above, which requires thereformatting step to loop back to the input side of the decision step312. In addition, each re-formatted copy of the data is assigned astorage location. For users desiring only virtual publication withoutbackup, as discussed above, data can be stored where it is mostconvenient and cost-effective to do so. It may be desirable to storecertain data copies on the originating system, thus conserving serverstorage resources. For example, it may be desired to virtually publishgraphic data only in thumbnail and low-resolution forms, avoiding theoverhead of storing voluminous graphic files on the server.

Before transmission, data is encrypted at step 318, using any of thewell-known methods available to the art. Finally, the data istransmitted, step 318. A preferred method of performing this step is toencrypt the data at the 128-bit level, using any of the widely availableproducts for accomplishing that process, such as those commerciallyavailable from VeriSign Inc., and to transmit it over a secure SSLconnection.

Automatic backup actions on the mobility server are shown in FIG. 4 b.This process is the responsibility of the data collection module 140shown in FIG. 2. At the outset, the data is received (step 320),decrypted (step 322) and then indexed (step 324). The index operationinvolves central index 164.

Creation and storage of metadata at step 326, interacting with metadatastore 167, is key to providing continuous availability of information.Choice of what elements to include in metadata are within the skill ofthose in the art, as required by particular applications.

The versioning subsystem, step 328, operates in conjunction with versionstore 168. Details of versioning systems are known in the art, but inone system according to the present invention, versioning is fullyconfigurable by the user to determine exactly how many versions of adocument are saved, and similar options.

Steps 332-338 collectively make up the virtual publication process 330,shown within a dotted-line box in FIG. 4 b. The key feature of thisprocess is that it does not simply back up or store data. Rather, datais made available for later use by other users. The distinction is clearin the art, as backup systems are characterized by narrow functionalprofiles, while publication denotes making the document available atleast to a group of users. As noted below, the fact that the system doesnot publish data directly to users has led to the adoption of the term“virtual publication” to describe this aspect of the invention.

The virtual publication process begins with determination of storageparameters, step 332, interacting with the profile store 166. Determinedhere are the formats in which to store the incoming data. A number ofmethods can be used to obtain that result, but here it is preferred thatthe member profile include that information, which avoids additionalprocessing overhead at this point. That listing could be obtained in anumber of ways, either directly or dynamically in cooperation with thetarget device inventory 130 of the mobility server (FIG. 2).

Next, the system obtains the required data instances, step 334. To dothis, the system compares the list of required formats from thepreceding step to the formats in which the agent transmitted data to themobility server. If additional data rendering is required, the systemhere determines where that rendering should be accomplished and overseesthe execution of that action. Generally it is expected that the agentwill have accomplished as much rendering as possible at the local hostlevel.

From here, the data is encrypted in step 336 and then stored in step338, employing central data store 162. Data storage is discussed in moredetail in connection with FIG. 2. In the case of data designated“virtual publication only”, the actual storage step is not carried out.

After the storage is complete, the system returns to monitoring statusin step 346. It is expected that users will maintain an open connectionbetween fixed members (and any mobile members maintaining an internetconnection, as can occur now with laptop users and in the future withother devices) and the mobility server, primarily to facilitate theautomatic backup process described below.

Distribution

The task of making data available to users is simple in a conventionalsituation—the data is stored in an accessible location, and users log into that system and download the data. In a mobile environment, however,that situation is not the norm. Users can access the system from deviceshaving a variety of data capabilities, in terms of device memory andscreen capabilities. The distribution process depicted in FIG. 5 dealswith such situations. This process is executed by two of the mobilityserver functional blocks shown on FIG. 2. The distribution phase, steps350-366, is overseen by distribution module 150; the tracking phase,steps 368-374 is managed by change management system 170.

The distribution phase is initiated by a user requesting a datadownload, in step 350. It should be noted that users should be affordedsufficient flexibility in presenting a data download request, so thatrequests can be made, for example, not only for data to be downloaded tothe device being employed by a user at that time, but also to anotherdevice associated with that user, or, via forwarding, to anotherlocation entirely. Also, the present description omits any mention ofsecurity procedures that should be implemented in connection with datadownloads, as such procedures are within the knowledge of those in theart. Based on security settings, one user can grant data sharingprivileges to a many or few other users as desired.

Next, step 352, is to determine whether the required data is located onthe mobility server or its associated data store (see FIG. 2). As willbe recalled, data may be stored at the server or at the user's location,based on criteria discussed in connection with FIG. 4. If data islocated somewhere other than at the mobility server, the decision steproutes program flow to step 354, where the data is retrieved. As data isreceived—not awaiting it in entirety—it will passed through the mobilityfor the remaining parts of the process, which allows the device to startreceiving a response sooner, not leading it to believe the data isunavailable.

Then the system determines formatting requirements for the download, atstep 356. This process requires several sub-processes, in that thecorrect format depends on the receiving device, which in turn should bepre-associated with a user, and the subject data, as modified by userpreferences. The system should know that User A, for example, uses aBlackBerry™ device, and if that user has requested download of an Excelspreadsheet, then the system should know that the data should bereformatted before transmission. The format determination is supportedby interaction with profile store 166. It is highly important that theformat data store also identify irreconcilable format problems. Forexample, a cellular telephone user may request download of a video file.Such data files are usually multiple gigabytes in length, far beyond thecapacity of basic telephone handset devices. The system must identifysuch situations and prevent both technical and user satisfaction issuesassociated with too much data. The system should be capable ofidentifying alternative courses of action in the event such impasses arepresented. For example, in the video file situation set out above,rather than simply noting that transmission of the video file was notallowed, the system could send one or more thumbnails extracted from thevideo or simply warn the user that a time-consuming and potentiallyexpensive operation is about to start. Other measures will suggestthemselves to those in the art.

If decision step 358 determines that data rendering is required, thesystem begins at step 360 by identifying the optimum location forconducting that process. That determination depends on a number offactors, including the type of data, file size, the respective overheadloads of potential rendering locations, and system rules or guidelines.Those of skill in the art will be able to fashion appropriate decisionalgorithms to implement such a determination routine.

Once the rendering location is selected, the system oversees therendering operation, step 362. If the data requires transmission toanother location, that transmission must be accomplished, and thenappropriate commands sent to whatever host equipment is involved. It isanticipated that most rendering will occur at the location where thedata is stored, whether at the desktop or server.

Finally, it must be determined whether the data is to be sent in theform of a data file or streamed to the user, decision step 357. Thatdetermination can be based on user input at the data request, or it canflow from the data type/equipment type combination, or the like. Mostsuch decisions are completely obvious and lend themselves to automateddetermination. For example, video data files are inherently unsuitablefor downloading to devices with limited storage capacity, such ascellphones or PDA's, but they can stream very nicely to such devices.Based on that decision, data is either downloaded as a file in step 364or streamed in step 366.

Once the data has been distributed to the user, the tracking phasebegins, under control of the change management module 170 (FIG. 2). Instep 368, all document actions, taken by either the server or by therecipient, are checked to determine whether that action requires analert to the originator or a third person (step 370). Typical actionsinclude document being delivered, deleted, saved, modified, or forwardedto a third party. If an alert is required, the system notifies the userwho requested that notification, at step 372. Of course, tracking islimited to actions that occur on the mobility server, as there is no wayof determining actions taken solely on the addressee's system. Trackingcontinues until receipt of a predefined event indicating the requestinguser has finished with the document, such as an indication that thedocument has been closed or deleted. That point ends thedistribution/tracking process, step 374.

CONCLUSION

While the present invention is disclosed by reference to the preferredembodiments and examples detailed above, it is understood that theseexamples are intended in an illustrative rather than in a limitingsense. Computer-assisted processing is implicated in the describedembodiments. Accordingly, the present invention may be embodied innetworks including software and hardware elements, systems includinglogic and resources to carry out interactions between fixed and mobiledevices; media impressed with logic to carry out network operations,data streams impressed with logic to carry out network operations, orcomputer-accessible services that carry out computer-assisted networkoperations. It is contemplated that modifications and combinations willreadily occur to those skilled in the art, which modifications andcombinations will be within the spirit of the invention and the scope ofthe following claims.

1. A network mobility system, for use with a private mobile network ofmember devices, comprising: a mobility server having a target deviceinventory store which includes an inventory of supported devices andindicating display and rendering capabilities of each of the supporteddevices, wherein the server receives a data file package from a networkmember outside the mobility server, the data file package including atleast one version of a data file, each version having a respectivedisplay format, wherein the server manages reformatting of the data fileinto an additional version having a display format which a particulardevice in the inventory has the capability to display or render, whereinthe server stores for subsequent distribution, the additional versionand at least one of the versions in which the data file was received,and wherein the server transmits in response to a request, to a targetone of the devices in the private mobile network, a version of the datafile which the target device has the capability to display.
 2. A systemaccording to claim 1, further comprising a plurality of network agents,resident on network members, in communication with said mobility server,wherein at least one the network agents is adapted to render a data filefrom a first version having a first display format into a second versionhaving a second display format.
 3. A system according to claim 2,wherein the at least one network agent is adapted to perform therendering for forwarding to the mobility server, the data file packageincluding both the first and second versions.
 4. A system according toclaim 1, wherein the display format of the data file additional versionis a display format which a device in the private mobile network has thecapability to display or render.
 5. A system according to claim 1,wherein the server stores for subsequent distribution, the additionalversion in association with all of the versions in which the data filewas received.
 6. A system according to claim 1, wherein the serverincludes at least one data storage module, wherein at least a portion ofthe data stored in said data storage module are identical data itemsstored with different display formats suitable for use on different onesof the supported devices.
 7. A system according to claim 1, wherein theserver further determines in dependence upon a retrieval request to sendthe data file to a given one of the supported devices which lacksfunctionality to display files in any of the display formats of theversions in which the data file is stored, and in response to suchdetermination, the server manages reformatting of the data file into afurther version having a display format which the given device has thecapability to display or render.
 8. A system according to claim 1, foruse where a first one of the data file versions received by the serverincludes an image having a particular resolution, and wherein theserver's management of reformatting includes functionality to develop alower resolution version of the image.
 9. A system according to claim 1,for use where a first one of the data file versions received by theserver includes a document in a native file format of a particularapplication program, and wherein the server's management of reformattingincludes functionality to develop a version of the document in a nativefile format of a different application program.
 10. A system accordingto claim 1, for use where a first one of the data file versions receivedby the server includes a spreadsheet in a native file format of aspreadsheet program, and wherein the server's management of reformattingincludes functionality to develop a plain text version of thespreadsheet.
 11. A system according to claim 1, for use where a firstone of the data file versions received by the server includes aspreadsheet in a native file format of a spreadsheet program, andwherein the server's management of reformatting includes functionalityto develop a rendered image version of the spreadsheet.
 12. A systemaccording to claim 1, wherein the server's management of reformattingincludes functionality to develop a PDF version of the data file.
 13. Asystem according to claim 1, wherein the server's management ofreformatting includes functionality to convert a video file from onevideo format to another.
 14. A system according to claim 1, wherein theserver's management of reformatting includes functionality to extract astill image from a video file.
 15. A system according to claim 1,wherein the server's management of reformatting includes: means forselecting, from among member devices of the private mobile network, anoptimum device for performing the additional rendering; and means foroverseeing the reformatting at the selected device.
 16. A networkmobility system, for use with a private mobile network of member devicesincluding first and second subsets of the member devices, comprising: aplurality of network agents resident on member devices in the first andsecond subsets; and a mobility server adapted for communicating with thenetwork agents, the network agents being outside the mobility server,wherein agents on member devices in the first subset include operablefunctionality to, in a virtual publication operation, render data filesinto different versions having different display formats, and agents onmember device in the second subset lack such operable functionality,wherein agents on member devices in the first subset further includeoperable functionality to, in the virtual publication operation,transmit to the mobility server data files in more than one version eachhaving a respective display format, and wherein the mobility server isadapted to receive and store in association with each other and forsubsequent distribution, the data files received from the agents in morethan one version.
 17. A system according to claim 16, wherein themobility server is adapted to store the data files at least in versionshaving display formats suitable for display on the second subset ofmember devices.
 18. A system according to claim 16, wherein the mobilityserver includes functionality to manage reformatting of received datafiles into additional versions having display formats suitable fordisplay on the second subset of member devices, and to store forsubsequent distribution, the additional version and at least one of theversions in which the data file was received.
 19. A system according toclaim 18, wherein the mobility server includes further functionality totransmit in response to a request, to a target one of the devices in theprivate mobile network, a version of the data file which the targetdevice has the capability to display.